CommonConversationRuntime

The conversation option entry is what we send to the client, one entry per choice.

This struct represents a logical participant in a conversation.

You can think of the FConversationBranchPoint as the owner of FClientConversationOptionEntry.

Template<> struct TStructOpsTypeTraits : public TStructOpsTypeTraitsBase2 enum { WithNetSerializer = true // For now this is REQUIRED for FConversationChoiceDataHandle net serialization to work };

The conversation choice reference is the closest thing there is to a link at runtime for a choice.

Information about a currently active conversation.

There may be multiple databases with the same entrypoint tag, this struct holds all of those nodes with the same matching tag name, so that the entry point is effectively randomized when there are multiple copies.

Used to store arbitrary structs of data in different contexts for a conversation.

The FConversationTaskResult encompasses the type of result along with any extra data we need for that kind of result, for example if we're giving the player a message and giving them a choice, what what message do we need to send.

Container for safely replicating script struct references (constrained to a specified parent struct)

A choice on a task indicates that an option be presented to the user when the owning task is one of the available options of a preceding task.

Wrapper methods from FConversationContext.

This is a database of conversation graphs and participants It is an asset and never instanced.

An active conversation between one or more participants

Represents a single runtime node in the conversation database.

Active conversation participants should have this component on them.

A registry that can answer questions about all available dialogue assets

A requirement is placed on a parent node to control whether or not it can be activated (when a link to the parent node is being evaluated, the requirement will be asked if it is satisfied or not)

Conversation settings.

Side effects are actions that are performed just after a task is executed (this allows state-altering or cosmetic actions to be mixed in to other nodes)

: CONVERSATION: Comment me

Task are leaf nodes of behavior tree, which perform actual actions

The requirement result.

The conversation task result type gives the conversation system the instruction it needs after running a task.