Forums | Moodkie Interactive

Here is the full Error message if it helps at all. But I will work on creating a smaller version. Thanks for sending the project over. In your case this is expected behaviour because you're moving GameObject with an ES3AutoSave Component to DontDestroyOnLoad. Because Auto Save is scene specific and...

Hi there, Sorry to hear you've been having issues. I'm assuming you're using Auto Save given your other comment. Auto Save is scene specific, so data saved in one scene won't overwrite data saved in another and you need to enable Auto Save in each scene in which you wish to save. However, given the ...

I am encountering this same error. This is my first time attempting to integrate Easy Save into a game, and it has been anything but easy for me. :cry: I used the steps in the Getting Started guide and went to the Easy Save 3 window, Auto Save, and clicked to add it to my scene. It added an Easy Sa...

Hey! Someone already figured out how to decrypt the save haha. Is there anyway to make this harder? The password is like 40 characters long. Well, to make it harder to obtain the decryption password use il2cpp (doesn't make it impossible, just harder) or don't store the save data locally. I am one ...

Unfortunately it's hard for me to understand what is happening without a way of replicating it or another other reports of the issue.

Please could you make a copy of your project and remove everything which isn't required to replicate the issue and send me that.

All the best,
Joel

Glad you managed to find the variable

All the best,
Joel

Hi there,

I've not seen this before. Just to check, is there an ES3ReferenceMgr Component attached to the Easy Save 3 Manager?

If so, please could you send me a project with replicates this on moodkie.com/contact.

All the best,
Joel

From that stack trace I can see that one of the variables you're saving (or a field of that variable) is a GameObject, and the issue is occurring when attempting to load one of it's Components. Specifically it looks like you might be trying to save a PlayMakerFsm Component, which isn't serializable ...

Hi there, We don't appear to have received any reports of behaviour like this when using caching apart from if a crash occurs with the app, meaning that any data stored to the cache since the last time you called ES3.StoreCachedFile() will be lost (this is expected behaviour). In this case I recomme...

You can find information on what types are supported (and by extension what types aren't supported) here: https://docs.moodkie.com/easy-save-3/es3-supported-types/ The biggest issue is usually when people save Components which aren't supported, or GameObjects with Components which aren't supported. ...