OGS – Dialogue & Quest Master

Interactive scenes that move from dialogue to gameplay

Dialogue & Quest Master is built for projects where conversations, objectives, and cinematics need to stay connected. It brings Unreal Engine 5 into a workflow for interactive stories, combining a dialogue editor, a quest framework, automation tools, and cinematic integration in one system. The result is a setup where plain text can become playable dialogue sequences without forcing a project into a rigid structure.

The framework is built entirely in C++ and Blueprints, and it is fully extensible. That makes it suitable for small prototypes as well as larger RPG-style projects. It is also part of the OGS ecosystem and integrates with Interaction Master, while OGS Core is required as the base framework.

What stands out immediately is how much of the narrative pipeline is already tied together. Dialogue, quests, statistics, and save state are all treated as connected parts of the same gameplay layer instead of separate systems that need to be stitched together later.

Dialogue creation with branching, conditions, and cinematic timing

The dialogue side uses a dedicated graph-based editor to help structure conversations visually. Conditions, actions, branching paths, skippable lines, character tags, and sub-graphs are all included, giving designers room to shape reactive dialogue without touching C++ code for every conversation change.

Cinematic support is built directly into the workflow. Body animations, MetaHuman facial animation, spatialized audio, and subtitles are supported natively. Subtitles can also be placed directly in Sequencer so they line up with level cinematics. That makes the system useful for scenes where dialogue is meant to land in sync with camera movement and performance timing.

Several workflow tools are included for faster iteration. Raw text can be pasted in to auto-generate nodes, voice lines can be generated through an ElevenLabs API key, facial animations can be linked automatically, and ARKit curves can be converted for custom facial rigs. The framework also adds a Random Branch Node for dynamic dialogue branching, which helps conversations feel less predictable when a scene needs variation.

Version 3.0 also brings broader improvements to the dialogue workflow: full network replication for dialogues, quests, and statistics, a refactored save system, massively improved graph editors, blueprint-style comments, multi-node edition, copy and paste, undo and redo, customizable fonts and colors, improved cinematic workflow and editor stability, and an improved camera system with bone tracking.

Quest logic, reminders, and tracked progress

Quests are handled in their own node-based editor, following the same visual approach as the dialogue tools. That makes it easier to design branching flows, completion logic, alternative paths, and dependencies without switching to a different style of workflow.

The quest layer includes a customizable Quest Journal, a tracked quest widget, and a notification system. Built-in tasks cover common structures such as talking to an NPC, reaching a location, or completing stat and achievement objectives, so projects can get started quickly while still keeping the logic open for extension in Blueprint or C++.

A quest reminder system was added in Version 3.0. When a task is active, an optional dialogue can be configured to play at random intervals and remind the player what to do. That small feature supports games where objectives need to stay clear without breaking the narrative tone.

Statistics, saving, and networked narrative state

The statistics system tracks gameplay events such as kills, items collected, interactions, and other events. These values are not isolated counters; they can drive dialogue conditions and quest objectives, which makes the narrative layer reactive to what the player has actually done.

All statistics are replicated and saved as part of the global narrative state. Version 3.0 extends that idea with full network replication for dialogues, quests, and statistics, so the state can move cleanly from server to clients.

The save architecture was redesigned as well. The entire narrative state, including dialogues, quests, progress, and stats, can be saved, loaded, replicated, and replaced with a different backend if needed. The system can work with Unreal’s SaveGame system, a custom database, or an external service by overriding a few functions. That flexibility is useful when a project needs to keep its narrative state inside an existing pipeline rather than adapting the pipeline to the plugin.

Built for production work and project-specific UI

Every interface is customizable, including the dialogue UI, quest journal, quest notifications, and tracked quest list. A centralized configuration asset lets teams change fonts, colors, backgrounds, icons, and layout to match the game’s identity. Controller-aware UI logic is included out of the box.

The framework is built for real production use, with all features accessible in Blueprints, full source code included, and a clean, documented architecture. It is positioned to work across FPS, RPG, survival, action-adventure, open-world, and similar project types without locking the project into a single genre structure.

Written documentation, video tutorials, and an active Discord community are available, along with a public roadmap. The community already includes 100+ developers using the framework, and the overall package is aimed at teams that want narrative tools, quest logic, statistics, and cinematic presentation to live in the same setup. For projects that need dialogue and objectives to respond to gameplay state while staying editable in both Blueprint and C++, that combination is the central advantage.