https://doc.cdryx.net/CdryxAIOUPlugin/cquestumodule/diagrams/index.html Overview Visual diagrams illustrating the internal architecture and runtime behavior of CQUESTUMODULE. 1. Class & Data Hierarchy Relationships between the quest manager, quest structs, quest steps, enums, delegates, and the Core interfaces. classDiagram direction TB class UCQuestManager { +TMap~FName, FCQuestStruct~ questMap +getInstance(AActor*) UCQuestManager* +createQuest(TMap questMap_) +clearAll() +activateAnyQuest() +proceedWithActorQuestAction() +proceedWithRoomQuestAction() } class ICQuestMaker { <<interface>> +proceedWithActorQuestAction()* +proceedWithRoomQuestAction()* } class ICPipeline { <<interface>> +doSequentially()* } class QuestUtility { <<static>> +proceedWithQuestAction(AActor*)$ +proceedWithQuestAction(FCRoomQuestContainer)$ } class FCQuestStruct { <<struct>> +FName questId +CQuestStatus status +CQuestInnerStatus questInnerStatus +FCBP_questCondition questCondition +TMap~FName, UCQuestStep*~ questStepMap +TSet~FName~ currentStepSet } class UCQuestStep { +FName questId +FName questStepId +CQuestStatus status +FName thingToInteractWith +FCBP_questStepActorAction stepActorAction +FCBP_questStepRoomAction stepRoomAction } class CQuestStatus { <<enum>> UNSET FAIL SUCCESS } class CQuestInnerStatus { <<enum>> UNSET ACTIVATED CLOSED } class FCRoomQuestContainer { <<struct from CCOREUMODULE>> +bool enterInRoom +UCAbstractRectangleMetadata* metadata } UCQuestManager . Hugo en-us