Good afternoon, I use Quest Machine and Easy Save 3, I complete a quest, I try to save the data, then I load the data, but nothing happens, the quest just becomes active, not completed. What am I doing wrong?
Save code:
Make sure your player’s Quest Journal component > Save Settings > Remember Completed Quests checkbox is ticked, and that a unique Save Key is assigned.
Make sure your player’s Quest Journal component > Save Settings > Remember Completed Quests checkbox is ticked, and that a unique Save Key is assigned.
If it’s not saving at all, the quest should not appear in the Quest Journal. (Unless you talk to the NPC and pick it up again.)
At what point in the loading process are you calling your ES loading code? If it’s in an Awake method, you may be calling it before the Quest Journal has initialized.
If it’s not saving at all, the quest should not appear in the Quest Journal. (Unless you talk to the NPC and pick it up again.)
At what point in the loading process are you calling your ES loading code? If it’s in an Awake method, you may be calling it before the Quest Journal has initialized.
I am using the latest version 1.2.32.2. I save manually after completing the quest, and load it about half a second after the Start method. There are no errors or warnings. All my quests have Current State = Active
I'm sorry; I must have missed the forum notification.
You could try ticking the Debug checkbox on the SaveSystem component and PlayerPrefsSavedGameDataStorer component. Then play in the editor and reproduce the issue. Review the Console logs. It will show unformatted JSON. You should be able to find the QuestJournal component's Key value. Make sure it lists the quests. If these are human-authored quests (made in the Quest Editor), the actual quest data won't be readable since it will be in a compressed format.
If that doesn't help, please send a reproduction project to tony (at) pixelcrushers.com.
Tony Li wrote: ↑Tue Dec 20, 2022 4:57 pm
I'm sorry; I must have missed the forum notification.
You could try ticking the Debug checkbox on the SaveSystem component and PlayerPrefsSavedGameDataStorer component. Then play in the editor and reproduce the issue. Review the Console logs. It will show unformatted JSON. You should be able to find the QuestJournal component's Key value. Make sure it lists the quests. If these are human-authored quests (made in the Quest Editor), the actual quest data won't be readable since it will be in a compressed format.
If that doesn't help, please send a reproduction project to tony (at) pixelcrushers.com.
It's strange, but in the new test project, saving worked, I will continue to try to find out the reason. And here's the question: Is it possible that the problem with saving is due to my own conditional scripts?
I also found a problem with the QuestControl script, when added to an object, it is not displayed in the inspector and the console gives errors:
As it turned out, the problem with saving is present in quests where I use my condition scripts. What is wrong in my script? I check the current active item in it.
Regarding your custom quest condition, QuestCondition is not a MonoBehaviour. You can't count on Awake() or OnEnable(). Can you rewrite it to eliminate those methods?