Architecture

The project is organized around a clear editor/runtime split, with graph assets and runtime playback as the core architectural boundary.

Assemblies: DialogSystem.Runtime and DialogSystem.Editor Core 3.0 has no required AI dependency

Repository structure

Path	Responsibility
`Assets/DialogGraphSystem/Scripts/Runtime`	Playback, UI, settings, history, transcripts, utilities.
`Assets/DialogGraphSystem/Scripts/Editor`	Graph authoring, import/export, settings editor, GraphView tooling.

Runtime data flow

Game code or UI event
    -> DialogManager.PlayDialogByID
    -> DialogGraph lookup
    -> Graph traversal
    -> DialogUIController
    -> DialogActionRunner
    -> OnLineShown / OnChoicePicked
    -> DialogueHistory
    -> Branch path tracking
    -> DialogGraphTranscriptBuilder

Editor authoring flow

DialogGraphLauncherWindow
    -> DialogGraphEditorWindow
    -> DialogGraphView
    -> Node views and edges
    -> DialogGraph asset plus node sub-assets
    -> Save / Load / Undo

Main extension points

IActionHandler implementations for custom gameplay actions
DialogActionRunner conversation and global action sets
replacement or extended UI around DialogUIController
new reveal effects implementing ITextRevealEffect
new transcript build modes in DialogGraphTranscriptBuilder

Coupling and technical debt notes

The runtime relies on specific Resources paths for settings and demo assets.
The graph authoring flow depends on UnityEditor.Experimental.GraphView, which works but is not future-proof long term.
Several systems assume the included prefab structures or field wiring patterns, so prefab replacement should be done carefully.

Suggested visuals

Graph editor overview

Best visual anchor for the editor/runtime split.