Quests and branching dialogue (dialog) for your NPCs, in one C++ plugin with its whole surface in Blueprint. Conversations are text scripts, quests are data assets, and both play in multiplayer and save into your save game.
The guide: heyheythere.com/docs/quest-dialogue, a fifteen-minute quickstart into the Third Person template, the script format, and every node and setting. Read it before you buy.
Quests
- Data assets: a title, a description and stages of objectives that run at once
- Required quests and tags to start one, tags given when it completes, repeatable quests
- Every state: inactive, active, completed, failed, abandoned; restart any quest
- Complete or fail one objective; an optional objective can fail without the quest
- Any number of quests at once, one of them tracked
Objectives from one node
- Report Quest Event with a gameplay tag and a count, from anything: a kill, a pickup, a door
- Every active objective on that tag, or a parent of it, counts it: nothing to subclass
- A Quest Trigger actor for reach-a-place objectives, a speaker for talk-to ones
Dialogue as text
- A .qds script: speakers, lines, numbered choices, labels and gotos
- Conditions on quest states and tags; lines start, advance, complete or fail quests
- Lines give and take tags and fire named events for Blueprint
- Diffs and merges in source control; an edited script reimports in one click
- A voice clip a line, moving on when it ends; all text FText, for the localization dashboard
Blueprint
- Every node, event and setting in Blueprint, and C++ for those who want it
- A quest and a talking NPC need no Blueprint graph and no C++
Multiplayer
- The server owns each player's quests, replicated to that player alone on the PlayerState
- Changes made on a client go to the server, or are refused if you turn client requests off
- Tested with two players on a listen server
Save
- One node puts every quest and tag into your own save game, one restores them
- A slot helper for a game without one
- A quest changed since the save loads what still fits
Default UI
- A dialogue box with choices, a quest log with track and abandon, an on-screen tracker
- UMG, built in C++; keyboard, mouse and gamepad through Enhanced Input
- Subclass any of them in a Widget Blueprint, or build your own on the same nodes
Debugging
- A Gameplay Debugger category: every quest, stage, objective and tag as they change
- Quest.List, Quest.Start, Quest.Complete, Quest.Fail and Quest.Report move a test along
- Saving a quest or importing a script lists its problems in the Message Log
The demo
- The village in the video: a fetch quest, a gate to hold that can be lost, a secret to keep or tell
- Save and load buttons, and two players on a listen server
- It ships in the plugin's Content/Demo folder (turn on Show Engine Content and Show Plugin Content)
- Epic's mannequins in a project made from the Third Person template, plain stand-ins otherwise
Engines and platforms
- Unreal Engine 5.6, 5.7 and 5.8, on Windows, Mac and Linux
Support through this page's comments or by email.