Creating save data means Dialogue in database stops updating

[bluebuttongames]

I was afraid you were gonna say that...

[bluebuttongames]

But I guess I could use that as a solution,

There's another problem though, when I add a new variable (say as part of DLC or an update) it comes through in any old save data which is loaded as "nil", not the new value that should be assigned.

[Tony Li]

Is the Dialogue Manager's Persistent Data Settings > Initialize New Variables checkbox ticked?

[bluebuttongames]

I don't have that setting:

[Tony Li]

Can you update?

It looks like you may be using version 1.x. The instructions to update from 1.x to 2.x are here: Updating From 1.x

I'll PM you access info for the latest 1.x version (1.9) if you can't update to 2.x.

[bluebuttongames]

I can try it, but I'm so close to launch I'm worried about how risky it is.

Does the update change the data structure in any way? I have .csv files out with localisers.

[Tony Li]

It doesn't change the data structure, but there are some small changes. Here are the release notes for version 1.x:

Version 1.x Release Notes

Look at the _README.txt file in the Dialogue System folder to identify your version. Then check the release notes for the later versions.

[bluebuttongames]

Do I need to do these upgrading from 1.x steps even if I'm only upgrading to 1.9?

[Tony Li]

If you're only updating to 1.9, you don't need to follow those upgrade steps. Just back up your project and then import version 1.9.

[bluebuttongames]

So, that got me some way out of the problems, but now I have others.

I have custom fields in quests relating to the day they were completed or their morality which now don't save because items/quests are no longer persistent so that I can fix any typos etc in their text fields.

I'm faced with now creating multiple variables for every quest individually to store this data.

Have I just architected this in a way that I shouldn't have? Do I have any other options?