Forums | Moodkie Interactive

hi, I'm trying to group all my save files inside a subfolder of the Persistent Data Path. I tried to do the following var settings = new ES3SerializableSettings("MySaveFolder"+System.IO.Path.PathSeparator+"myfile.es3"); ES3.Save("mykey", value, settings); but instead of...

Ok so as long as I know what I'm doing, I can let the autosave to "OnApplicationQuit" and still save at other times in my code. Great news, thanks.

Thanks,
followup question: in the autosave doc it is said that it's better to set the "Save Event" to "none" when calling ES3AutoSaveMgr.Current.Save via code. Does this mean I should avoid calling Save via code in OnApplicationQuit and OnApplicationLoad?

Hi, if I understand correctly, if I want to work with multiple save slots, I have to use settings. My understanding is that for the ES3 class I can either Load things using a specific settings instance myValue = ES3.Load("myKey", mySettings, defaultValue); Now if I wanted to just change th...

Hi, I'm wondering how I should go about using the auto saver when working with additive scenes. I have a "SceneLoader" scene which contains some managers and is responsible for handling the loading of my actual game scenes, and when I switch to another scene, I unload the current scene, an...

@Berg if you want to autosave scriptable object references that may change at runtime on the scene, then you can drag and drop the SO asset into the Reference Manager if you want to save a scriptable object that was modified at runtime (an inventory for example), then you have to code it manually. T...

Thanks a lot for your help. It would be really nice if there was an extra chapter in the documentation talking about how to work with ScriptableObjects. I know there's a few things to say about using ScriptableObjects as anything else than static data containers, but there's definitely a lot of peop...

Ok I've been playing around to make the basic project and I've discovered something interesting. If the SO is referenced by an object on the scene, it is added to the ES3 Reference manager, however if it is modified at runtime and changed to reference an object that was not referenced DIRECTLY (so e...

Well, changing the save path for the autosave seems to solve the problem though, so at leat there's that. I'm using both because autosave is rather convenient but doesn't allow me to save/load SO's (since it only saves a reference) however I've not looked into custom types yet. I suppose it's possib...

Hi there, If you're using both then you should ensure that you're saving to separate files. All the best, Joel Oooooooh ok I see. Is it mentioned somewhere in the documentation? because that's not very clear. I suppose what happens then is that the file gets completely overwritten by the autosave. ...