You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 7, 2026. It is now read-only.
🔗 Is your feature request related to a specific issue?
The dialogue backends (Ink, Yarn Spinner) are responsible for the story's logic and content, but they have no ability to display anything on the screen. A bridge is needed to connect the dialogue flow to the user interface.
💡 Feature Description
Create a DialogueUIView component or system that acts as an intermediary between the active dialogue runner (Ink or Yarn Spinner) and the actual UI elements.
Expected outcome or effect: Correct display of dialogue lines, character names, and player choices in the UI, decoupled from the narrative backend.
Specific implementation ideas: The following definitions are for reference only and are subject to change. Implementation could include:
The DialogueUIView will subscribe to events from the dialogue runner, such as OnLineStart, OnChoicesPresented.
When an event is received, it will update the appropriate UI elements (e.g., set the text of a TextMeshPro component, create and populate choice buttons).
It will also handle user input, such as clicking a choice button, and report it back to the dialogue runner to advance the story.
Usage scenarios or benefits: This decouples the narrative logic from the presentation layer. You can completely change the look and feel of your dialogue box without touching the story scripts, and vice-versa.