Pixel Crushers Forum

I added a Dialogue System Saver component to my Save System game object. When my player saves the game, I can see in the Console that it actually does save all of the quest states and what not. And it works when the player leaves to the main menu and loads up their save slot. The quest states are saved.

The problem is when the game is uploaded as an application and the player quits, or if it's uploaded as a WEBGL and the user exits the browser, even after saving, if they load up the game again and load their file, the Quest States will be completely reset. Oddly enough, their health and coins are still reloaded though.

Am I saving quest states correctly? Should I be saving them similarly to how I save coins and hp? Thank you for any help.

Hi,

At runtime, the first Dialogue Manager to appear during play will survive scene changes and replace any Dialogue Manager GameObjects that are in subsequently-loaded scenes.

Make sure the first Dialogue Manager (typically in the first scene in your project's build settings) is configured the way you want, including with a Dialogue System Saver component. I recommend making this Dialogue Manager into a prefab variant and using it in your other scenes, too, so you don't have different Dialogue Manager configurations in different scenes.

Tony Li wrote: ↑Wed Nov 02, 2022 7:30 pm Hi,

At runtime, the first Dialogue Manager to appear during play will survive scene changes and replace any Dialogue Manager GameObjects that are in subsequently-loaded scenes.

Make sure the first Dialogue Manager (typically in the first scene in your project's build settings) is configured the way you want, including with a Dialogue System Saver component. I recommend making this Dialogue Manager into a prefab variant and using it in your other scenes, too, so you don't have different Dialogue Manager configurations in different scenes.

That did it, thank you!

Glad to help!