Other Save & Load System

So I made a clicker game and I want to save & laod the data from my game. But I cant find a way to save the status of my upgrade buttons (button.SetActive) I just cant. So if anyone can help me with that. I already have the other like the clicks and high score but not the buttons.

 

Don't save your buttons and don't serialize any UI elements. Your UI should be separated from your game data and reflect and modify the game data.

Your game data might have like a configuration object that represents the configuration options the user has selected. This data object is the thing that you serialize and save, not the button. Your GUI should show the current value and update the value in its onclick handler.

 

^ ^ ^ ^ This.

- Have data.
- Allow input to modify data.
- Have routines to output and use that data to make your game behave.
- Save and load only the data.

Load/Save steps:

https://forum.unity.com/threads/save-system-questions.930366/#post-6087384

An excellent discussion of loading/saving in Unity3D by Xarbrough:

https://forum.unity.com/threads/save-system.1232301/#post-7872586

Loading/Saving ScriptableObjects by a proxy identifier such as name:

https://forum.unity.com/threads/use...lds-in-editor-and-build.1327059/#post-8394573

When loading, you can never re-create a MonoBehaviour or ScriptableObject instance directly from JSON. The reason is they are hybrid C# and native engine objects, and when the JSON package calls

new

to make one, it cannot make the native engine portion of the object.

Instead you must first create the MonoBehaviour using AddComponent<T>() on a GameObject instance, or use ScriptableObject.CreateInstance<T>() to make your SO, then use the appropriate JSON "populate object" call to fill in its public fields.

If you want to use PlayerPrefs to save your game, it's always better to use a JSON-based wrapper such as this one I forked from a fellow named Brett M Johnson on github:

https://gist.github.com/kurtdekker/7db0500da01c3eb2a7ac8040198ce7f6

Do not use the binary formatter/serializer: it is insecure, it cannot be made secure, and it makes debugging very difficult, plus it actually will NOT prevent people from modifying your save data on their computers.

https://docs.microsoft.com/en-us/dotnet/standard/serialization/binaryformatter-security-guide