How it works

Quests are defined in a DataTable using the plugin structure. Each row corresponds to a quest and contains its configuration: objectives, unlocking conditions, rewards, and automations. During play, the quest subsystem reads that DataTable and retains the state of every quest. Blueprint functions let you inspect and modify that state: a quest can therefore be set to In Progress, Completed, Abandoned, Failed, or back to Not Obtained according to your project logic.

The ADS Quest Participant Component is placed on the owner that takes part in a quest. For a quest giver, enter the quests its owner can offer in QuestsToGive. For a quest objective, enter its TargetType and TargetIDs to identify what type of objective its owner represents and which objectives it matches. The same actor can be both a giver and an objective. The component then queries the subsystem: it displays a giver indicator when one of its quests can be obtained, or an objective indicator when it matches the active objective of an in-progress quest.

During play, the system automatically sends dispatchers so that your Blueprints can react without manually monitoring data:

• OnStateChanged is called when a quest changes state.
• OnTracked is called when a quest is added to tracking, and OnUntracked when it is removed.
• OnTrackedClear is called when the tracked-quest list is completely cleared.
• OnObjectiveUpdated is called when objective progress is recalculated or manually notified.
• OnObjectiveStepReached is called when every objective in a stage is reached.
• OnAllObjectivesReached is called when every stage in a quest is reached.
• OnQuestsCompleted is called after one or more quests have actually moved to the Completed state; it also provides the available rewards.
• OnLocked and OnUnlocked are called when quests are locked or unlocked respectively.
• OnCompletionConflict is called when several auto-completable quests require the same consumable resources and the system cannot choose which one should complete.

These dispatchers can, for example, update a quest journal, tracking UI, dialogue, or world markers.