GameSaver and DialogueSystemController persistentDataSettings conflict

[marche4ever]

Hello, I was investigating why my Quest fields would not save, then I found out that both GameSaver and DialogueSystemController writes to PersistentDataManager.includeAllItemData on Awake(), and there is no guarantee of execution order. In my case, I set it to true for GameSaver, but it was set to false by DialogueSystemController. I feel like this workflow should probably be improved.

[Tony Li]

Hi,

GameSaver and LevelManager are both essentially deprecated in favor of the save system. Can you adjust your configuration to eliminate GameSaver and LevelManager? In place of GameSaver, use SaveSystem or SaveSystemMethods. In place of LevelManager, use SaveSystem.LoadScene.

[marche4ever]

Hi,

GameSaver and LevelManager are both essentially deprecated in favor of the save system. Can you adjust your configuration to eliminate GameSaver and LevelManager? In place of GameSaver, use SaveSystem or SaveSystemMethods. In place of LevelManager, use SaveSystem.LoadScene.

Oh... I didn't know that... I thought GameSaver works like any other Saver component such as PositionSaver. I'm removing it now, Thanks!

[Tony Li]

Glad to help. Sorry for the confusion with those components!