Forums | Moodkie Interactive

Thank you for Easy Save 3.

For taking logic out of components, for taking about 50% of work out of me, and for being quite extensive.

+1, when loaded, Animator loses "Controller" field My solution: have singleton with RuntimeAnimatorController field public class EasySaveReferenceHelper : MonoBehaviour { public static EasySaveReferenceHelper Instance; public RuntimeAnimatorController CharRuntimeAnimController; private voi...

I promise it's the last thing :), more about UI than functionality: Ability to open AutoSave window by "Manage Auto Save Settings" button from ES3Prefab script ; not only from E3AutoSave (that would speed things up as you enable AutoSave for prefabs > and you can start defining fields righ...

OK got it working

the solution was to load scene with navmesh first, then to load (using AutoSave) navmeshAgents after one frame

apparently this error was on my side

thanks for support

Thank you for everything, I don't know if it's a feature request or a bug: Support for nested prefabs and prefab versions If you create a prefab and then add a prefab child to it, then if you enable AutoSave for both prefab and prefab child, and click Refresh in ES3RefernceMgr, ES3ReferenceMgr and A...

Is there a way to trigger it?

my case is that I have GameObjects for items of a character, as children of this character. They are dynamically taken / given between characters.

If not, I'll manage, thanks for all the work you do anyway

*note from the author of this feature request: Collapsable Hierarchy (https://moodkie.com/forum/viewtopic.php?f=14&t=2201) is more important feature than this feature (comments), imho

I searched documentation and forum but couldn't find explanation on behavior of "Save Children" checkbox on ES3AutoSave script; I used it and it worked but Does it save only supported components that are in /Easy Save 3/Types down the hierarchy? Does it save everything down the hierarchy w...

Sure: to add comments why you added certain fields to AutoSave. For example you enable SpriteRenderer.color & .sprite and you write comment "Because [this unit-generation asset I imported from AssetStore] uses .color and .sprite Or if you created a field inside script only for some post-loa...

Feature: Add comments in autosave window (which would show in that window where you check which fields you want to AutoSave)

then they would go into autogenerated Type file, e.g. after "//"