Dialogue system by Marcus Aas Jensen.

This dialogue system is a versatile tool integrated to Unity's engine to build story based interactions in a video game.

You can watch the demo on Youtube too: https://www.youtube.com/watch?v=QhQQnyrjZJc

What's possible to create with this dialogue system:

• Create branching dialogues with dialogue choices using the integrated Dialogue Graph Editor.
• Dialogue path save system.
• Have different characters in a dialogue with each the possibility to change sprite, voice (sound, pitch), reactions, and emotion.
• Text typer with control over typing pace in play mode.
• Character speaker to control current character's "voice" (one sound repeated) with typer synchronization and default pace.
• Add multiple "command" tags to different text of the dialogue to have more control over storytelling.
• Workflow based on scriptable objects (save & load).

Open the Dialogue Graph Editor window in the top menu "Graph > Dialogue Graph Editor".

You will see a blueprint with a menu at the top. The only existing node is the "START" node which is the node that directs where the dialogue should start.

A simple node is a visual representation of a dialogue composed of a list of messages. It can start from other nodes and you can connect it to a single other dialogue node.

Create a simple node in the top menu with the button "Create Simple Node". A simple node will appear on the blueprint. This node is composed of a disconnected input port, an empty dialogue, and a disconnected output port.

You can connect the START node to the simple node by dragging your mouse click from the start node port named "Next" to the simple node's input port. This indicates the dialogue will start the simple node's dialogue at the very beginning of the narration. Now, you know how you can build a chain of nodes by creating and connecting outputs to inputs. Also, it is possible to close the dialogue UI and reopen it at the next interaction using the option at the bottom of the simple node.

A multiple choice node is a simple node with multiple possible outputs. Each outputs has a text and must be a path to another node. Basically, when the player enters a multiple choice node, he will have to choose between the different text options.

Create a multiple choice node in the top menu with the button "Create Multiple Choice Node". A multiple choice node will appear on the blueprint. It is similar to the simple node. You can add an option using the "New Choice" button. Then, an option appears inside the node. Now you can edit the text and connect its port to other nodes. You can add up to 5 choices (otherwise it is too much). Also, you can remove it using the "Remove" button next to the option.

At the end of the dialogue, it will automatically show the options you added. However, an option must be connected to another node, otherwise, it will be removed on save. In case the player goes back to the same node, it is possible to disable already chosen options at the bottom of the node.

Edit the dialogue of a specific node by clicking on the "Edit Dialogue" button of the node. This will open a new window presenting an empty list of messages.

Add a new message to the list. Then you can write the character's name, the message to show, add the command tags (see how to use them in the Command tags section) with the option of showing or not the character ("Hide Character"). Make sure to write correctly the character's name or the dialogue system will not know which character is speaking. If the message list is empty, it will close the dialogue at that node or show the possible choices for the case of a multiple choice node.

You can close the dialogue messages window to save.

To save your narrative, you must write the name of your file in the top menu. Then, you can save by clicking on the "Save data" button. All of your narratives will be saved in the path "Assets/Resources/Dialogue System Data/Narratives/". You can load an existing narrative from the resource path by writing the file's name and clicking on the "Load Data" button in the top menu.

Before testing your narrative, open your narrative scriptable object's inspector and list all the characters present in your narrative.

The "Path To Checkpoint" property is the path that will be created when the player makes choices in the narrative. You can use its value or remove it to reset the narrative.

"Is Narrative End Reached" is also an option you must reset if the player has reached the end of the narrative and that you want to reset it for testing.

"Start From Previous Narrative Path" is an option when the player closed the dialogue and reopens it to start from where he left off.

Do not hesitate to use the scene templates I have provided in the project. Every time you save your narrative, you will need to reference it to a GameObject's component inheriting from the DialogueMonoBehaviour class. You can use DialogueStarter GameObject to start immediately the dialogue or the Character GameObject (InteractableDialogue) where you need to interact with the character (Interactable) to start. You must test in Play Mode.

Invokes the event associated with a certain name you have defined in a dialogue monobehaviour that uses the narrative.

Replace the onevent text by the name of your event you have previously defined (name as a string).

"Something is happening...<event:onevent> That was strange!"

Here is a script that extends the class DialogueMonoBehaviour that allows the player to interact with a character. Then you can define your event at runtime in the script with the name you have used in your tag.

Pause the text typer for a certain time.

Replace the pause text by one of the following pause types.

tiny: 0.1s
short: 0.25s
normal: 0.666s
long: 1s
read: 2s

"Wait... <p:normal> You're kidding right?"

Changes the typer text's speed, otherwise the speed is the default typer pace.

Replace the speed text by a real number.

The lower the value, the faster the typer.

"PLEASE <sp:0,1>I BEG YOU!"

Animates the text in between by the provided animation and the default text animator speed, amount and sync values.

Here is a Wobble animation example...

Replace the animation text by one of the following animation types.

None
Shake
Wobble
Wave
PingPong
Flicker
Spiral
Jitter

Tip

It is possible to use the TextAnimator component to test your animation values on the default text message in Editor Mode. Make sure to disable animation testing before entering Play Mode.

When you have decided the values to use in your dialogue, you can add other parameters in your tag:

<anim:animation a:amount s:speed>...</anim>

speed is the speed of the animation (real number).

amount is how much the animation is exagerated (real number).

<anim:animation a:amount s:speed sync:synchronize>...</anim>

synchronize is the animation synchronization of all letters in between (true or false).

"<anim:wobble s:1 a:2.5 sync:false>I'm feelin' dizzy right now...</anim>"

Changes the "emotion" of the current speaking character. The emotion must be defined in the Character's Scriptable Object in the list of character's states. If not defined, it will automatically use the default character's state that must be defined too.

Make sure the default character scriptable object is well defined and is referenced in the NarrativeController component.

Replace the emotion text by one of the following emotion types.

Default
Hidden
Happy
Neutral
Angry
Scared
Fearful
Sad
Disgusted
Annoyed
Surprised
Curious
Warm
Evil

When the tag is used, the character will have the associated character face sprite, reaction sound (plays one time), and speaking pitch. You will have to define each emotion with your own assets in the character's scriptable object.

"<em:evil>I am the danger."

Replaces the tag's position by a stored value named value. The variable must be defined in the Scriptable Singleton "DialogueVariableData.asset". If not defined, the value will be "X". The variables can be of type int, float or string. Boolean variables are not included.

You can manipulate these variables using C# script.

public class ExampleSceneScript : MonoBehaviour
{
  private void Awake()
  {
    DialogueVariableData.Instance.RemoveAllDialogueVariables();
    DialogueVariableData.Instance.AddDialogueVariable("cost_coffee", 1.5f);
    DialogueVariableData.Instance.AddDialogueVariable("cost_bread", 1);
    DialogueVariableData.Instance.AddDialogueVariable("character", "John");
    DialogueVariableData.Instance.AddDialogueVariable("tmp", 0);
    DialogueVariableData.Instance.RemoveDialogueVariable("tmp");
    DialogueVariableData.Instance.ListAllDialogueVariables();
  }
}

"This coffee costs exactly <val:cost_coffee>💲."

Resulting DialogueVariableData.asset values:

Plays one shot the sound named sound when the text typer arrives at tag's position. The Sound effect must be defined with a name in the Scriptable Singleton "DialogueAudioData.asset" (sound effect list).

"So I was saying...<sfx:fart> Woops, I farted."

Plays in loop the music named score when the text typer arrives at tag's position. The music must be defined with a name in the Scriptable Singleton "DialogueAudioData.asset" (music list).

"<music:emotional>Life is like a box of chocolate..."

Stops any current looping music.

"*music playing*...</music>It's not your fault."

Of course, it is possible to use the default tags to customize your TextMeshPro text like colored, italic, bold, rotated etc.

The latest update was the Unity Event tag feature, which actually groups all of the functionalities I initially wanted to make. You can use any function on your Unity Events to execute Timelines, use your custom camera shakes etc. Hope you enjoy the system.