Pixel Crushers Forum

Hi,

My example code above treats any quest that isn't procedurally generated as being "bugged":
I wasn't sure exactly what your criteria were for determining if a quest is bugged. You can change this line, or remind me what's identifiable about a bugged quest and I'll try to provide the right line of code for it.

I gavent changed anything on ORKQuestMachineSaveData, the issue now is that provably quest machine tries to load the quest from ORKQuestMachineSaveData while previously were saced via quest journal maybe?

So trying to resolve this first before going changing ORKQuestMachineSaveData to fix bugged quests

Hi,

I think both components (ORKQuestMachineSaveData and QuestJournalForORK) were saving the quest data. So it should be okay to tick that checkbox on QuestJournalForORK and rely only on ORKQuestMachineSaveData's copy of the quest data.

It seems that Journal was saving, since checking this option on the new Journal, it doesnt load any of the player's quests. So, it will work for new saves, but the old saves are doomed this way

Okay, so to confirm:

1. With the QuestJournalForORK's "Allow ORK Quest Machine Save Data To Save" checkbox ticked, newly saved games work, and they save through the ORKQuestMachineSaveData component on the Quest Machine GameObject.

2. However, old saved games do not restore any quests at all?

Is that correct?