Quest System Framework

The framework addresses a recurring problem in Unreal Engine projects: quest systems that couple objective tracking logic directly to level actors or Player Controllers, making them difficult to test in isolation and expensive to extend.

The architecture separates concerns into three components: QuestManagerComponent (authoritative state), QuestObjectiveComponent (individual condition tracking), and QuestUIBridge (Blueprint-accessible event dispatchers for UMG without coupling UI to the data layer).

Objective completion is driven by GameplayEvent payloads fired from gameplay code. The QuestObjectiveComponent registers listeners on initialization for specific GameplayTag events. When a tag matching an objective's condition fires (e.g., Gameplay.Kill.Orc), the component increments its counter and evaluates completion. This eliminates the common pattern of checking quest conditions in Tick, which scales poorly with many active objectives.

Quest branching uses a node graph evaluated at runtime. Each quest has a directed graph of objective nodes. Completing an objective triggers evaluation of its outgoing edges, each carrying a condition. The first edge whose condition is satisfied activates the next objective node. This handles non-linear quest structures (choice branches, optional objectives) without complex switch statements in game code.