User Guide (Version 1.13)

Communication System

This topic references tools and features that are legacy. If you want to use legacy tools in Lumberyard Editor, disable the CryEntity Removal gem. To learn more about legacy features, see the Amazon Lumberyard Legacy Reference.

AI communication is about playing sound/voice and/or animations at the right times in the course of the game.

Setting up communication for an AI agent requires the following steps:

  • General set up:

    • Define communication channels. Channels are used to track the status of communication events for an AI.

    • Define communications. Communications detail specifically what activity should occur (and how) when the communication is called for. Communications are grouped into configurations.

    • Set up voice libraries. Voice libraries support localized dialogs, subtitles, and lip-syncing.

  • Specify communication types for an AI using AI properties:

    • Point an AI's CommConfig property to a communication configuration, which contains the set of communications for that AI.

    • Point an AI's esVoice property to a voice library to use for that AI.

  • Trigger a communication event:

    • Specify the name of a communication channel for the event.

    • Specify the name of a communication to fire.

Communications, channels, and voice libraries are defined in a set of XML files. At game start-up, the directory Game/Scripts/AI/Communication and all subfolders are scanned for XML files containing these configurations.

Defining Communication Channels

A communication channel determines whether an AI can play a communication at a given moment, depending on whether or not the communication channel is occupied. Channels are a self-contained concept, independent of other AI communication concepts. They have a sole purpose: to be in one of two possible states, "occupied" or "free".

AI communication channels are defined in an XML file stored in Game/Scripts/AI/Communication. The SDK includes a template channel configuration XML file, called ChannelConfg.xml. Communication channels are configured in a hierarchy of parent and child channels. The hierarchical structure determines how a channel's occupied status affects the status of other channels (for example, a parent of an occupied child channel).

Channel Elements & Attributes

Communication channels are defined in a <ChannelConfig> element with the following attributes:


Channel name.




Minimum time (in seconds) that the channel should remain occupied after a communication has been completed.


Time (in seconds) that the channel should remain occupied after it has been flushed. This value overrides the imposed silence time (minSilence) after playing a communication. If not specified, the value set for minSilence is used.


Minimum time (in seconds) to restrict AI agents from playing voice libraries after starting a communication.


Flag indicating that AI agent communication restrictions from the script should be ignored.


Type of communication channel. Valid values are "personal", "group" or "global".


Game/Scripts/AI/Communication/ChannelConfig.xml <Communications> <ChannelConfig> <Channel name="Global" minSilence="1.5" flushSilence="0.5" type="global"> <Channel name="Group" minSilence="1.5" flushSilence="0.5" type="group"> <Channel name="Search" minSilence="6.5" type="group"/> <Channel name="Reaction" priority="2" minSilence="2" flushSilence="0.5" type="group"/> <Channel name="Threat" priority="4" minSilence="0.5" flushSilence="0.5" type="group"/> </Channel> <Channel name="Personal" priority="1" minSilence="2" actorMinSilence="3" type="personal"/> </Channel> </ChannelConfig> </Communications>

Configuring Communications for an AI

Communication configurations determine what communication activity AI agents can perform and how it will manifest. Communications for a particular type of AI are grouped into configurations. For example, your game might have both human and non-human AI agents, each with its own set of communication activities. In this scenario, you might group all the human communications into a configuration object named "human" while communications for non-humans might be grouped into a "non-human" configuration. For a particular AI, you'll specify the configuration to use with the AI's CommConfig property. With this configuration structure, you can define a communication (such as "surprise") differently in each configuration so that, when triggered, the communication activity fits the AI involved.

For each communication, you also have the option to define multiple variations of action and specify how the variations are used.

AI communication channels are defined in one or more XML files stored in Game/Scripts/AI/Communication. The SDK includes a template channel configuration XML file, called BasicCommunications.xml.

Communication Elements & Attributes

Communications are configured using the following elements and attributes:


Communication configurations are grouped into <Config> elements and use the following attributes. Each configuration must contain at least one communication.


Configuration name, which can be referenced in the AI's CommConfig property.


A communication is defined in a <Communication> element with the following attributes. Each communication should contain at least one variation.


Communication name.


Method to use when choosing a variation. Valid values include "Random", "Sequence", "RandomSequence" or "Match" (uses only the first variation).




Similar to choiceMethod.


Boolean flag.


Each variation is defined in a <Variation> element with the following attributes.


Animation graph input value.






Boolean flag indicating whether or not the AI should look at the target during the communication.


Method that determines when communication is finished, such as after the communication type has finished or after a time interval. Valid values include "animation", "sound", "voice", "timeout" or "all".


AI behavior to disable during communication. Valid values include "movement", "fire", "all", or "none".


Valid values include "signal" or "action".




Game/Scripts/AI/Communication/BasicCommunications.xml <Communications> <!--sound event example--> <Config name="Welcome"> <Communication name="comm_welcome" finishMethod="sound" blocking="none"> <Variation soundName="sounds/dialog:dialog:welcome" /> </Communication> </Config> <!--example showing combined animation + sound event (needs state using action/signal in the animation graph)--> <Config name="Surprise"> <Communication name="comm_anim" finishMethod="animation" blocking="all" forceAnimation="1"> <Variation animationName="Surprise" soundName="sounds/interface:player:heartbeat" /> </Communication> </Config> </Communications>

Setting Up Voice Libraries

To support localized dialogs, subtitles, and lip syncing, you need to set up voice libraries. Once set up, you can assign a voice library to an AI (or entity archetype) using the AI's esVoice property.

Voice libraries are defined in a set of XML Excel files stored in GameSDK/Libs/Communication/Voice. The SDK includes a template voice library file at GameSDK/Libs/Communication/Voice/npc_01_example.xml.

Each voice library must include the following information.


Localization type for this library.

File Path

Location where the sound files for this library are stored.


Communication name associated with a sound file.

Sound File

File name of a sound file, listed by signal.


Comment field used to describe or illustrate a sound file.



Language American English
File Path languages/dialog/ai_npc_01/
Signal Sound File SDK NPC 01 Example
see_player_00 i see you
see_player_01 hey there you are
see_player_02 hey i have been looking for you
pain_01 ouch
pain_02 ouch
pain_03 ouch
death_01 arrrhh
death_02 arrrhh
death_03 arrrhh
alerted_00 watch_out
alerted_01 be careful
alerted_02 something there

Setting Communication for an AI

An AI's communication methods are set using the AI agents properties. You can set AI properties in several ways. For information about using Lumberyard Editor to set AI properties, see Using Database View to Set AI Communication

Set the following properties:

  • CommConfig – Set this property to the name of the communication configuration you want this AI to use. Communication configurations are defined in XML files in Game/Scripts/AI/Communication, using <Config> elements.

  • esVoice – Set this property to the name of the XML file containing the voice library you want this AI to use. Voice libraries are defined in XML files in GameSDK/Libs/Communication/Voice.

Turning Animation and Voice Off

Communication animation and/or voice can be turned off for an AI agent using the agent's Lua script (as in the example below) or the entity properties in Lumberyard Editor Editor.


Game/Scripts/Entities/AI/Shared/BasicAITable.lua Readability = { bIgnoreAnimations = 0, bIgnoreVoice = 0, },

Triggering a Communication Event

To trigger a communication event, use the goalop communicate with the following attributes. Note that communication animations are not played if the AI is currently playing a smart object action.


Name of the communication to trigger (sound, voice, and/or animation). Communication names are defined in an XML file referred to by the CommConfig property of this AI.


Communication channel being used by this AI. An AI's communication channel is defined in an XML file in Game/Scripts/AI/Communication.

expirity (expiry)

Maximum allowable delay in triggering the communication when the communication channel is temporarily occupied. If a communication can't be triggered within this time period, it is discarded.

To trigger communications using flow graph logic, use the Flow Graph node AI:Communication.


<GoalPipe name="Cover2_Communicate"> <Communicate name="comm_welcome" channel="Search" expirity="0.5"/> </GoalPipe>


To get debug information on AI communication issues, use the following console variables (ai_DebugDraw should be set to "1"):

  • ai_DebugDrawCommunication

  • ai_DebugDrawCommunicationHistoryDepth

  • ai_RecordCommunicationStats

Debug output is shown in the console as illustrated here:

Playing communication: comm_welcome[3007966447] as playID[84] CommunicationPlayer::PlayState: All finished! commID[-1287000849] CommunicationManager::OnCommunicationFinished: comm_welcome[3007966447] as playID[84] CommunicationPlayer removed finished: comm_welcome[3007966447] as playID[84] with listener[20788600]


[Warning] Communicate(77) [Friendly.Norm_Rifle1] Communication failed to start

You may get this message or a similar one if your AI's behavior tree calls a communication but the communication configuration is not set up properly. In this example message, "77" refers to line 77 in your AI's behavior tree script (or goalop script). This line is probably communication trigger such as this:

<Communicate name="TargetSpottedWhileSearching" channel="Reaction" expirity="1.0" waitUntilFinished="0" />

Some things to check for::

  • Does the specified communication name "TargetSpottedWhileSearching" exist in your communication configuration files (XML files located in Game/Scripts/AI/Communication/)?

  • Check the CommConfig property for the AI. Is it set to the name of a <Config> element defined in your communication configuration files? If so, is the communication name "TargetSpottedWhileSearching" defined inside this <Config> element? This issue, calling communications that aren't configured for the AI is a common source of this error.

  • Check the communication's variation definition. Does it point to a resource (animation, sound) that exists? If using a voice library, does it point to a valid voice library file name?