Forums | Moodkie Interactive

I attached an image that can explain my assumptions. - I save and load the Item Database only. - Let's say we have Item, Item Type, and Category. All three are Scriptable Objects created on the inspector - Item has a variable for Item Type and Category. - Item is part of the dictionary 1. When I sav...

Hello Joel, Thanks for the answer! My assumption was that ES3 would not touch Scriptable Object files that were used (and saved) by reference and only load the reference without touching the file. But it seems that ES3 is reloading the object too even if it's a reference. Now, why do you think happe...

Okay, so I did get some Warnings that were hidden in between other warnings that I had. The warning I'm getting is this one: Reference for ContainerType with ID 2082928117821905327 could not be found in Easy Save's reference manager Now, this seems to be a very picky bug. It happens with certain ite...

Ah, it seems that it was a problem with the latest update that you already fixed. So you can omit the last message about the FormatException. I'll try to reproduce the other error in a smaller scale

Hello! - I'm not getting warning when loading - The Scriptable Object exist in the file system as it's created using the Create/Menu option. I have been trying to reduce the project to find the reason the bug is happening but it has been challenging, it certainly appears every time I load. If I clos...

Hello, I'm not sure if you have seen this before, but when I'm doing a load a variable is being removed. I have a Scriptable Object (item) that is being stored in a Dictionary. Now, one group of items within this Dictionary have one variable that holds another Scriptable Object (like an enum) as a v...

Whenever you changed a type you would need to change its appropriate ES3Type to reflect this. However, as long as you're using the try/catch statement included by default in the ES3Type, previous save data will still be valid. What do I need to do to change the ES3Type? I was talking about the one ...

Correct, I was talking about needing parameterizedless constructors. Based on this, a couple of questions: - Do you see any problems with having multiple constructors? It seems that I can just choose the one with the least amount of info required when modifying the ES3UserType on the ReadObject - Wh...

Hello, hello. I have two questions: - I'm trying to make sense of the constraint on parameterized constructors. If I'm adding a constructor is because I want it to be initialized by a specific implementation, and very likely there would not be default values. In addition to this, I will have an Asse...

Hi there, The best way to manage this very much depends on the structure of your project. However, the most common structure is to have one script which manages all of the saving, rather than getting individual objects to save themselves. This may also make it easier to ensure that dependencies are...