Quest System Plugin
Unreal Engine · C++ · Slate · Blueprint · node editor · Articy
- Editor
- Node-based, C++/Slate
- Accessible from
- Blueprint + C++
- Designed for
- New quest types
Problem
Branching narratives are data, not code. If every new quest type requires a programmer to open the editor, designers stop experimenting and the narrative system stops growing.
Constraint
The plugin had to live inside Unreal Engine as a C++ module with a Slate editor, and it had to be equally usable from Blueprint and C++ — different users, same underlying model. It also needed to connect to dialogue data produced elsewhere (Articy) without becoming an Articy-only tool.
Decision
I separated the data model from the editor and the runtime:
- A node-based editor in Slate for authoring branching structure.
- A runtime model that works from both Blueprint and C++.
- An extension point for new quest types, so adding a type does not mean rebuilding the editor.
- An Articy wrapper that brings external dialogue data and events into the quest system, keeping the quest plugin independent of the dialogue source.
Verification
The plugin was used in production game projects, from both Blueprint and C++ sides. The Articy path was exercised against real dialogue data, confirming that external events could drive quest state without embedding Articy into the core plugin.
Result
A reusable quest system shipped across titles, with designer tooling that survives new quest types.
The transferable lesson: designer tooling is systems work. The editor is a UI over a data model — get the model right and the UI stays cheap.